In @apps/frontend/src/renderer/components/task-form/ClassificationFields.tsx:
- Around line 64-158: Replace all hardcoded user-facing strings in
ClassificationFields.tsx with i18n keys: swap Label text ("Category",
"Priority", "Complexity", "Impact"), SelectValue placeholders ("Select
category", "Select priority", "Select complexity", "Select impact") and the
helper paragraph ("These labels help organize...") for translation lookups
(e.g., t('task.category'), t('task.selectCategory'), t('task.helper') or your
repo's key naming). Import and use the project's translation helper (e.g.,
useTranslation or t) at the top of the component and call it where Label,
SelectValue and the paragraph currently use literal strings; ensure you add
consistent translation keys (task.category, task.selectCategory, task.priority,
task.selectPriority, task.complexity, task.selectComplexity, task.impact,
task.selectImpact, task.labelsHelper) to the locale files.

In @apps/frontend/src/renderer/components/task-form/TaskFormFields.tsx:
- Around line 127-129: The declared descriptionRef in TaskFormFields is unused;
either remove its declaration or actually attach it to the Textarea so it’s not
dead code. If the intent is to control focus from this component, attach
descriptionRef to the Textarea via the ref prop (or convert Textarea to
forwardRef if needed) and update any consuming code to use the same ref;
otherwise simply delete the line that creates descriptionRef to clean up the
unused variable.
- Around line 228-233: The success message is hardcoded in TaskFormFields.tsx
where pasteSuccess controls the UI; replace the literal "Image added
successfully!" with a translated string (e.g., using the existing i18n
hook/utility used in this component such as t('...') or useTranslation()) so it
uses a translation key like "taskForm.imageAddedSuccess"; update the JSX that
renders when pasteSuccess is true to call the translation function and pass any
needed interpolation instead of the hardcoded text.
- Around line 235-250: The TaskFormFields component contains hardcoded user
strings in the Label, Input placeholder, and the explanatory paragraph; replace
those literals with i18n translation keys by importing and using your
translation hook/function (e.g., useTranslation/t) inside TaskFormFields and
call it where Label, Input and the paragraph render (refer to the Label, Input,
and the surrounding paragraph elements and keep existing props like
id={`${prefix}title`}, value={title}, onChange={onTitleChange} and disabled).
Add descriptive keys such as taskForm.title.label, taskForm.title.optional,
taskForm.title.placeholder and taskForm.title.help (or your project’s key naming
convention) and use t(...) for each string so the UI reads from the translations
instead of hardcoded text.

In @apps/frontend/src/renderer/components/task-form/useImageUpload.ts:
- Around line 136-144: The setTimeout used to reset setPasteSuccess in the
useImageUpload hook can fire after the component unmounts and cause state
updates on an unmounted component; modify the hook to track mounted status or
store the timeout id and clear it on cleanup: create a mounted ref (e.g.,
isMountedRef) set true on mount and false on unmount (or store timeoutId and
call clearTimeout in cleanup), check isMountedRef.current before calling
setPasteSuccess(false) (or clear the timeout in the hook's cleanup), and ensure
this logic is wired into the same scope where setPasteSuccess is invoked inside
the paste handling code in useImageUpload so no state update occurs after
unmount.

In @apps/frontend/src/renderer/components/TaskCreationWizard.tsx:
- Around line 559-618: The Git options UI uses hardcoded English strings;
replace them with i18n lookups by importing and using the project's translation
hook (e.g., useTranslation / useTranslations -> t) at the top of
TaskCreationWizard and swap the literal texts inside the button (where
setShowGitOptions/showGitOptions is used), the Label for "Base Branch
(optional)", the SelectValue placeholder and the SelectItem content that
currently render "Use project default", and the help paragraph text; create
appropriate translation keys (e.g., taskCreation.gitOptions.title,
taskCreation.gitOptions.baseBranchLabel,
taskCreation.gitOptions.useProjectDefault, taskCreation.gitOptions.help) and
pass the runtime baseBranch/projectDefaultBranch values into the translation
placeholders where needed (for the badge and placeholder).
- Around line 249-253: The hardcoded charWidth = 8 in TaskCreationWizard (used
with lines[currentLineIndex], currentLineIndex, paddingTop, lineHeight,
paddingLeft and rect.width - 300) can misplace the autocomplete; replace the
magic constant with a real measurement—either compute the per-character width
using a canvas 2D context and measureText for the component's current font or
integrate a caret-position utility (e.g.,
textarea-caret-position/textarea-caret) to get the exact caret coordinates; then
use that measured horizontal offset instead of currentLineLength * charWidth
when computing left so autocomplete aligns reliably across fonts and sizes.

In @apps/frontend/src/renderer/components/TaskCreationWizard.tsx:
- Around line 551-562: autocomplete.position is computed from descriptionRef but
descriptionRef is never attached to the textarea in TaskFormFields, so the
FileAutocomplete popup will be mispositioned or error; fix this by wiring the
ref into TaskFormFields: accept a ref (or a prop like descriptionRef) and attach
it to the textarea element (use React.forwardRef if TaskFormFields is a
component), ensure the parent passes the same descriptionRef used to compute
autocomplete.position, and add a null-guard where the position is computed so
you don’t call getBoundingClientRect on a missing ref; this ensures
FileAutocomplete receives a correct position and avoids runtime errors.
- Line 113: TaskCreationWizard declares descriptionRef but never passes it into
TaskFormFields, so descriptionRef.current stays null and the autocomplete
positioning (which reads textarea.getBoundingClientRect() and computed styles)
fails; fix by adding a prop to TaskFormFields (e.g., descriptionRef?:
React.RefObject<HTMLTextAreaElement>) and forwarding that ref to the internal
textarea element inside TaskFormFields, then pass the existing descriptionRef
from TaskCreationWizard into <TaskFormFields descriptionRef={descriptionRef}
.../>; also add a null check before using descriptionRef.current in the
autocomplete positioning code (or alternatively implement an
onDescriptionCursorChange callback prop if you prefer callback approach).
- Around line 424-430: The span in TaskCreationWizard that renders @mentions
currently sets color via both className ("text-info-foreground") and an inline
style (style={{ color: 'hsl(var(--info))' }); remove the redundant inline style
and rely on the CSS utility class for color consistency (or vice versa if you
prefer inline styles); update the span (the element with key={i} and
className="bg-info/20 text-info-foreground rounded px-0.5") to use only one
color approach.
- Around line 442-443: Replace the hardcoded user-facing strings in the
TaskCreationWizard component with i18n translation keys: import and use the
existing i18n hook (useTranslation) in TaskCreationWizard and swap each literal
(e.g., "Create New Task", "Describe what you want to build...", "Draft
restored", "Start Fresh", "Hide Files", "Browse Files", "Cancel", "Creating...",
"Create Task", "Git Options (optional)", "Base Branch (optional)", the
base-branch help text, "Please provide a description", "Failed to create
task...") for t('taskCreation.xxx') keys; add corresponding entries in the
locale JSON files (en/*.json and fr/*.json) following the project's key naming
convention (e.g., taskCreation.title, taskCreation.description,
taskCreation.draftRestored, taskCreation.startFresh, taskCreation.hideFiles,
taskCreation.browseFiles, taskCreation.cancel, taskCreation.creating,
taskCreation.createTask, taskCreation.gitOptions.title,
taskCreation.gitOptions.baseBranch, taskCreation.gitOptions.help,
taskCreation.errors.missingDescription, taskCreation.errors.createFailed), and
update every occurrence referenced in the review (lines ~442, 461-472, 487, 494,
500-503, 576-578, 596-619) to call t(...) instead of inline strings.

In @apps/frontend/src/renderer/components/task-form/TaskFormFields.tsx:
- Around line 217-219: The aria-label translation key in the TaskFormFields
component is missing the tasks namespace; update the call that sets aria-label
(inside the remove image button/handler in TaskFormFields) to use
'tasks:images.removeImageAriaLabel' instead of 'images.removeImageAriaLabel' so
the i18n lookup is explicit and consistent with the rest of the tasks namespace.
- Around line 184-186: The translation key used in the TaskFormFields component
is missing the explicit namespace prefix; update the call to the i18n translator
(the t(...) invocation that currently uses 'images.pasteHint') to use the
namespaced key 'tasks:images.pasteHint' so it always resolves to the correct
namespace regardless of namespace order; locate the t call inside the <p
id={`${prefix}description-help`} ...> block and replace the key string only,
leaving the platform check for the shortcut unchanged.

In @apps/frontend/src/renderer/components/task-form/useImageUpload.ts:
- Around line 109-113: The error message for invalid image types in
useImageUpload uses a hardcoded string; replace it with the app's i18n call
(e.g., t or formatMessage) so the message is localized and still includes
ALLOWED_IMAGE_TYPES_DISPLAY; update the call in the block where
isValidImageMimeType(file.type) is checked to call the translation helper (or
use a provided i18n prop/context) and pass ALLOWED_IMAGE_TYPES_DISPLAY as an
interpolation parameter to the localized string instead of the hardcoded English
text.
- Around line 141-143: The catch in useImageUpload currently swallows the error
and emits hardcoded messages; update the catch to accept the error (e.g., catch
(err)), call onError?. with i18n keys instead of literal strings (use the
appropriate translation keys for pasted vs dropped images), and log the error
for debugging (use the existing logger or console.error) including context
(e.g., options.isFromPaste and file info) so the actual exception is preserved
and traceable.

In @apps/frontend/src/renderer/components/TaskCreationWizard.tsx:
- Around line 156-194: Extract the two async helpers fetchBranches and
fetchProjectDefaultBranch out of the useEffect and wrap each in useCallback so
they are stable and reusable: create const fetchBranches = useCallback(async ()
=> { ... }, [projectPath, setIsLoadingBranches, setBranches]) that calls
window.electronAPI.getGitBranches and sets state, and const
fetchProjectDefaultBranch = useCallback(async () => { ... }, [projectId,
projectPath, setProjectDefaultBranch]) that calls
window.electronAPI.getProjectEnv and, on fallback,
window.electronAPI.detectMainBranch; then have the useEffect simply call
fetchBranches() and fetchProjectDefaultBranch() when open && projectPath, and
ensure the useEffect dependency array includes open, projectPath, projectId and
the two callbacks.
- Line 515: The descriptionPlaceholder in TaskCreationWizard is hardcoded;
replace it with an i18n translation key (e.g.,
"taskCreation.descriptionPlaceholder") by adding that key to your localization
files and using the translation hook/utility already used in the component
(e.g., useTranslation or t) to pass the translated string into the
descriptionPlaceholder prop; update TaskCreationWizard to import/use the
translator and swap the literal string for
t('taskCreation.descriptionPlaceholder') so the instructional text (including
the "@" mention hint) is localized.

In @apps/frontend/src/shared/i18n/locales/fr/tasks.json:
- Around line 129-130: The translation files contain duplicate keys
"creation.title" and "wizard.createTitle" with identical strings; decide whether
to consolidate into a single key or document distinct usage: search for
references to creation.title and wizard.createTitle in the codebase, remove one
key and update callers to the chosen canonical key (or keep both but add a
comment in the fr and en JSON explaining their distinct contexts), and ensure
you update any tests or components that reference the removed key such as UI
screens or wizard components to use the retained key.

In @apps/frontend/src/renderer/components/task-form/useImageUpload.ts:
- Around line 82-87: The merged `errors` memo currently depends on the object
identity of `errorMessages`, so inline callers (e.g., TaskFormFields) invalidate
`errors` each render and thus still recreate `processImageItems`; fix the hook
by stabilizing the dependency list: replace the single-object dep
`[errorMessages]` in the useMemo that produces `errors` (and the similar memo at
182-183) with a deterministic primitive-level dependency (for example use the
specific string fields or Object.values(errorMessages) as the dependency array)
so the merged `errors` only changes when actual message text changes;
alternatively, change the hook API to accept individual string props instead of
an object or require callers to wrap `errorMessages` in useMemo — choose one
approach and apply consistently to `useMemo` that builds `errors` and any
memo/callbacks that depend on it (e.g., `processImageItems`) so they stop being
invalidated by object identity churn.
- Around line 140-170: When deriving the file extension from file.type in the
image processing block (around blobToBase64/createThumbnail and before
resolveFilename), sanitize the MIME subtype so SVGs and other +suffix types
produce correct extensions: get the subtype via file.type.split('/')[1], then if
it contains a '+' take the substring before the '+' and normalize to lowercase;
if the result is empty fall back to 'png'. Use that sanitized extension when
building baseFilename (used before resolveFilename and when pushing newImages
entries).
- Around line 63-69: DEFAULT_ERROR_MESSAGES currently contains hardcoded English
strings; update useImageUpload to build its fallback errorMessages via the i18n
translation function (e.g., useTranslation or i18n.t) instead of literals.
Replace the static DEFAULT_ERROR_MESSAGES with a runtime default assembled
inside the useImageUpload hook using the existing translation keys from
tasks.json (e.g., 'tasks.maxImagesReached', 'tasks.invalidImageType',
'tasks.processPasteFailed', 'tasks.processDropFailed'), and then merge that
translated default with the incoming errorMessages prop so callers still
override specific messages.

In @apps/frontend/src/renderer/components/TaskCreationWizard.tsx:
- Around line 156-200: The useEffect fetchBranches flow can leave
isLoadingBranches true if the dialog closes before fetch finishes because the
finally block is skipped by the isMounted guard; update the effect so the
cleanup always resets loading: keep setting isLoadingBranches(true) at the start
of fetchBranches, remove the guarded setIsLoadingBranches(false) from the
finally block, and instead call setIsLoadingBranches(false) unconditionally
inside the useEffect cleanup; retain the isMounted/isActive checks only for
mutating state like setBranches and setProjectDefaultBranch in fetchBranches and
fetchProjectDefaultBranch to avoid setting state on unmounted components.
- Around line 239-272: handleDescriptionChange computes popup coords in
textarea-local space but applies them as absolute/viewport coords; update the
positioning to convert to viewport coordinates by adding the textarea bounding
rect offsets and subtracting textarea scroll offsets before calling
setAutocomplete. Specifically, in the handleDescriptionChange closure (uses
descriptionRef, detectAtMention and setAutocomplete) compute top = rect.top +
paddingTop + currentLineIndex * lineHeight + extraOffset - textarea.scrollTop
and left = rect.left + paddingLeft + Math.min(currentLineLength * charWidth,
rect.width - popupWidth) - textarea.scrollLeft, then pass those values into
setAutocomplete.position (clamped with Math.max(0, ...)). Alternatively, if you
prefer content-relative placement, render FileAutocomplete inside the textarea's
positioned ancestor and keep current content-relative math; ensure you handle
rect.top/left and textarea.scrollTop/scrollLeft in whichever approach you
choose.